powerstep

---

Power Step Click

Power Step Click demo application is developed using the NECTO Studio, ensuring compatibility with mikroSDK's open-source libraries and tools. Designed for plug-and-play implementation and testing, the demo is fully compatible with all development, starter, and mikromedia boards featuring a mikroBUS™ socket.

---

Click Library

• Author : Stefan Filipovic
• Date : Apr 2025.
• Type : GPIO type

Software Support

Example Description

This example demonstrates the use of the Power Step Click board by driving the motor in both directions for a desired number of steps.

Example Libraries

• MikroSDK.Board
• MikroSDK.Log
• Click.PowerStep

Example Key Functions

• powerstep_cfg_setup This function initializes Click configuration structure to initial values.

  void powerstep_cfg_setup ( powerstep_cfg_t *cfg );

• powerstep_init This function initializes all necessary pins and peripherals used for this Click board.

  err_t powerstep_init ( powerstep_t *ctx, powerstep_cfg_t *cfg );

• powerstep_reset_device This function resets the device by setting the RST pin logic state.

  void powerstep_reset_device ( powerstep_t *ctx );

• powerstep_drive_motor This function drives the motor for the specific number of steps at the selected speed.

  void powerstep_drive_motor ( powerstep_t *ctx, uint32_t steps, uint8_t speed );

Application Init

Initializes the driver and resets the device.

void application_init ( void )
{
    log_cfg_t log_cfg;  
    powerstep_cfg_t powerstep_cfg;  

    LOG_MAP_USB_UART( log_cfg );
    log_init( &logger, &log_cfg );
    log_info( &logger, " Application Init " );
 
    // Click initialization.
    powerstep_cfg_setup( &powerstep_cfg );
    POWERSTEP_MAP_MIKROBUS( powerstep_cfg, MIKROBUS_1 );
    if ( DIGITAL_OUT_UNSUPPORTED_PIN == powerstep_init( &powerstep, &powerstep_cfg ) ) 
    {
        log_error( &logger, " Communication init." );
        for ( ; ; );
    }
 
    powerstep_reset_device ( &powerstep );
 
    log_info( &logger, " Application Task " );
}

Application Task

Drives the motor clockwise for 100 slow steps and 300 medium speed steps and then counter-clockwise for 400 fast steps with a 1 second delay on driving mode change. All data is being logged on the USB UART where you can track the program flow.

void application_task ( void )
{
    log_printf ( &logger, " Move 100 steps clockwise, speed: slow\r\n\n" );
    powerstep_set_direction ( &powerstep, POWERSTEP_DIR_CW );
    powerstep_drive_motor ( &powerstep, 100, POWERSTEP_SPEED_SLOW );
    Delay_ms ( 1000 );
 
    log_printf ( &logger, " Move 300 steps clockwise, speed: medium\r\n\n" );
    powerstep_set_direction ( &powerstep, POWERSTEP_DIR_CW );
    powerstep_drive_motor ( &powerstep, 300, POWERSTEP_SPEED_MEDIUM );
    Delay_ms ( 1000 );
 
    log_printf ( &logger, " Move 400 steps counter-clockwise, speed: fast\r\n\n" );
    powerstep_set_direction ( &powerstep, POWERSTEP_DIR_CCW );
    powerstep_drive_motor ( &powerstep, 400, POWERSTEP_SPEED_FAST );
    Delay_ms ( 1000 );
}

Application Output

This Click board can be interfaced and monitored in two ways:

• Application Output - Use the "Application Output" window in Debug mode for real-time data monitoring. Set it up properly by following this tutorial.
• UART Terminal - Monitor data via the UART Terminal using a USB to UART converter. For detailed instructions, check out this tutorial.

Additional Notes and Information

The complete application code and a ready-to-use project are available through the NECTO Studio Package Manager for direct installation in the NECTO Studio. The application code can also be found on the MIKROE GitHub account.

---